Features
- Custom Event Metadata
- Enable / Disable Zones
- Android features
- Foreground Service
- iOS features
- App Restart Notification
Custom Event Metadata
Custom event metadata is a feature which is available in the Rezolve Point SDK for our customers to set additional event-specific metadata to our location events. For further information refer to Custom Event Metadata
It is recommended to set the Custom Event Meta Data before starting GeoTriggering or Tempo.
Maximum 20 entries can be set in custom event metadata. If more than 20 entries are set, Rezolve Point SDK throws an error as: Only 20 CustomEventMetaData fields are allowed.
BluedotPointSdk.setCustomEventMetadata({
orderId: "order_123",
storeId: "store_456",
customerId: "789"
})
Enable / Disable Zones
An app may optionally disable (and later re-enable) Zones by calling setZoneDisableByApplication. For further information refer to Enable or disable Zones documentation (Android | iOS)
const zoneIdToDisable = "your_zone_id";
const disableZone = true;
BluedotPointSdk.setZoneDisableByApplication(zoneIdToDisable, disableZone);
If you want to check if a Zone is enabled or disabled you can use the method isZoneDisablebyApplication as below
const zoneIdToDisable = "your_zone_id";
BluedotPointSdk.isZoneDiableByApplication(zoneIdToDisable)
.then(isDisable => {
if (!isDisable) {
BluedotPointSdk.setZoneDisableByApplication(zoneIdToDisable, true)
}
})
.catch(error => console.error('Error', error))
Android Features
Foreground Service
GeoTriggering can run without a linked foreground service. Linking one can reduce location-update latency, but do so only if your app independently qualifies to use that foreground service type under current Google Play policy; geofencing alone does not qualify as of October 28, 2026. Without a linked service, GeoTriggering can use background-worker mode when ACCESS_BACKGROUND_LOCATION is granted, though updates may have higher latency; otherwise, it is limited to foreground operation. The Tempo service requires a linked foreground service to start.
Since plugin version 4.0.0, the plugin no longer declares, starts, or owns a foreground service notification itself (the androidNotification builder method has been removed from both GeoTriggeringBuilder and TempoBuilder). Ownership of the foreground service moved to your app: your app declares its own <service> in the Android manifest, starts it, displays its own persistent notification, and links it to the SDK via ServiceManager.getInstance(context).linkForegroundService() (native) or BluedotPointSDK.linkForegroundService() (JS).
- GeoTriggering runs in background-worker mode with or without a linked foreground service — linking is optional and only reduces location-update latency.
- Tempo fails to start if no foreground service is linked.
- There is a single, shared link state — if your app uses both GeoTriggering and Tempo, they share one linked service.
For full setup instructions — including Android manifest changes, implementing your own foreground service, and linking it to the SDK — refer to the Migration guide to 4.0.0.
iOS Features
App Restart Notification
Rezolve Point SDK includes a method for apps to display app restart notification to user after app termination. For further details refer to iOS Features – App restart
The App restart method (iOSAppRestartNotification) is included in the GeoTriggeringBuilder. It should be set up before starting Geo-triggering.
This feature is not available in Tempo.
const geoTriggeringService = new BluedotPointSdk.GeoTriggeringBuilder()
geoTriggeringService
.iOSAppRestartNotification(
"notification title",
"button text content"
)
.start(
() => console.log("On success callback"),
(error) => console.error("On error callback")
)